Skip to content

Conversation

TylerLeonhardt
Copy link
Member

This moves us to use the latest preview of PowerShellGet v3 and the compat PSGet module

@TylerLeonhardt
Copy link
Member Author

:(

image

@TylerLeonhardt
Copy link
Member Author

TylerLeonhardt commented Sep 2, 2020

I added a Get-Module and gmo -list PSGet as a way to make sure the compat module works. Is this the best way?

Ah I see, it gives a warning, nice:

image

but also :( for the error. @JamesWTruher?

@alerickson
Copy link
Member

I like to run (get-command find-module).module.modulebase to make sure the module that's actually loaded is the right one.

@TylerLeonhardt
Copy link
Member Author

@alerickson Good to know!

@alerickson
Copy link
Member

alerickson commented Sep 2, 2020

I guess in this context it might make more sense to run ((get-command find-module).module).Version

@TylerLeonhardt
Copy link
Member Author

This is an odd error to me. Why is it spelled "Powershell" in the path?

@alerickson
Copy link
Member

alerickson commented Sep 2, 2020

Okay, just updating with convo Tyler and I had offline: beta9 is the latest psget release that handles some unix path changes, there is however, a bug with the -debug param in Install/Save (I realize it's not being used right now, just a warning)

- pwsh: |
Install-Module -Scope CurrentUser -Force -AllowPrerelease PowerShellGet
Install-Module -Scope CurrentUser -Force -AllowPrerelease CompatPowerShellGet
Install-Module -Scope CurrentUser -Force -AllowPrerelease -AllowClobber PowerShellGet
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need -AllowClobber for PSGet since it's entirely new cmdlet names

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'll scale better once PSGet v3 ships with PowerShell.

@TylerLeonhardt
Copy link
Member Author

ok I'm gonna stop here for now. Looks like we have some more work:

  1. PSGallery version problem (beta10 is being treated as the version between beta1 and beta2 instead of after beta9)
  2. PSGet doesn't register PSGallery by default (forcing me to run Register-PSResourceRepository -PSGallery)
  3. Looks like either the compat module or the main module are prompting for something even though I specified -Force

@rkeithhill
Copy link
Contributor

PSGet doesn't register PSGallery by default (forcing me to run Register-PSResourceRepository -PSGallery)

Surely that's a bug, right? I know, don't call you Shirley.

@TylerLeonhardt
Copy link
Member Author

@rkeithhill personally I agree with you. I think PSGet v3 should register PSGallery by default. I only did it in the commit to see what would happen if it was already registered.

@rjmholt rjmholt marked this pull request as draft December 17, 2020 18:16
@andyleejordan andyleejordan deleted the move-to-psget-3 branch September 9, 2025 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants